Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a54f8554a6f8a8fe4c0b87b230ad0f224b1d598c52d059758d8840bc9c0f9b5

Tx prefix hash: 4c5308cf7a64cf2f00a724e0d6903061277b2d072369d5413ff98f34e92dd40a
Tx public key: 1b1375ee5ef812c79212fd8b9033040e418113d19074dbdb0a61d6e21130acb6
Timestamp: 1738182636 Timestamp [UCT]: 2025-01-29 20:30:36 Age [y:d:h:m:s]: 00:141:06:06:10
Block: 1207887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100882 RingCT/type: yes/0
Extra: 011b1375ee5ef812c79212fd8b9033040e418113d19074dbdb0a61d6e21130acb60211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 573e58896e099f70978351afd5ba19b638f2b9e1749ec7669180b54039b3c3ef 0.600000000000 1694614 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": 1207897, "vin": [ { "gen": { "height": 1207887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "573e58896e099f70978351afd5ba19b638f2b9e1749ec7669180b54039b3c3ef" } } ], "extra": [ 1, 27, 19, 117, 238, 94, 248, 18, 199, 146, 18, 253, 139, 144, 51, 4, 14, 65, 129, 19, 209, 144, 116, 219, 219, 10, 97, 214, 226, 17, 48, 172, 182, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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