Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e81091b116b6cdfccc7e5beffb47a18ad1482c5e57be67d6785eec0cd4ddc6b

Tx prefix hash: cd13682ef58c54df79dd032dc400008ca63ffbcbbc85f3e9cda0155ec87b4caa
Tx public key: ae4ca992a025d2170783b90da3089c8435ea47c7011f359920b791bee2b0c951
Timestamp: 1742397520 Timestamp [UCT]: 2025-03-19 15:18:40 Age [y:d:h:m:s]: 00:318:02:50:17
Block: 1242784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224991 RingCT/type: yes/0
Extra: 01ae4ca992a025d2170783b90da3089c8435ea47c7011f359920b791bee2b0c951021100000006f7071dc6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30c7cd7ee3d0cf42061f85f09be6d690a2c937982e02bbe5a611a8882fd48aad 0.600000000000 1729761 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": 1242794, "vin": [ { "gen": { "height": 1242784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30c7cd7ee3d0cf42061f85f09be6d690a2c937982e02bbe5a611a8882fd48aad" } } ], "extra": [ 1, 174, 76, 169, 146, 160, 37, 210, 23, 7, 131, 185, 13, 163, 8, 156, 132, 53, 234, 71, 199, 1, 31, 53, 153, 32, 183, 145, 190, 226, 176, 201, 81, 2, 17, 0, 0, 0, 6, 247, 7, 29, 198, 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