Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b0cf488da77aefe47c5fa8a62c6fb566bca242d32cfb7bc203c3280e7eebf01

Tx prefix hash: 550de3f76fb450303749a70da625608081c92c92a4e139c08b8e13f369d38da0
Tx public key: fbbaa8afe88ebdc6289dc4b72669499dee22d24eda49b97c252ea9e0f41dfb61
Timestamp: 1711814910 Timestamp [UCT]: 2024-03-30 16:08:30 Age [y:d:h:m:s]: 01:222:00:48:00
Block: 989720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417344 RingCT/type: yes/0
Extra: 01fbbaa8afe88ebdc6289dc4b72669499dee22d24eda49b97c252ea9e0f41dfb6102110000000f0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c516012cf69e55f4f26293e403144bcd1af7de8caec847519a5e91cafa51c93 0.600000000000 1450038 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": 989730, "vin": [ { "gen": { "height": 989720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c516012cf69e55f4f26293e403144bcd1af7de8caec847519a5e91cafa51c93" } } ], "extra": [ 1, 251, 186, 168, 175, 232, 142, 189, 198, 40, 157, 196, 183, 38, 105, 73, 157, 238, 34, 210, 78, 218, 73, 185, 124, 37, 46, 169, 224, 244, 29, 251, 97, 2, 17, 0, 0, 0, 15, 0, 17, 5, 91, 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