Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 2bdcab465815c3c03f8aed79b38d2c51cafe60c2bd19039a51fc489ecdc7c2f9

Tx prefix hash: 7f5c66aae617ac96f75bdcb4edb043b5f56c073689a1e2d132aeb69657683142
Tx public key: 648c29cedc850a2359a82120f2fca34cad928bea1642efbc7411f7d4cca4c860
Timestamp: 1715575691 Timestamp [UCT]: 2024-05-13 04:48:11 Age [y:d:h:m:s]: 00:340:01:06:49
Block: 1020902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243042 RingCT/type: yes/0
Extra: 01648c29cedc850a2359a82120f2fca34cad928bea1642efbc7411f7d4cca4c86002110000000341ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e3c8b286a0a05c3cd7d4cd1e67d6f86e08d5a47b9c97719dafc304d805a0a64 0.600000000000 1485027 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1020912, "vin": [ { "gen": { "height": 1020902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e3c8b286a0a05c3cd7d4cd1e67d6f86e08d5a47b9c97719dafc304d805a0a64" } } ], "extra": [ 1, 100, 140, 41, 206, 220, 133, 10, 35, 89, 168, 33, 32, 242, 252, 163, 76, 173, 146, 139, 234, 22, 66, 239, 188, 116, 17, 247, 212, 204, 164, 200, 96, 2, 17, 0, 0, 0, 3, 65, 238, 28, 155, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8