Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b58ef05e526e193b3723eca3c28ec36dc1f517a21264bfdee36bd75fdb5239a

Tx prefix hash: 9f9743a9c53a9b9d9980b72943aea73e562fc8dd324e9519eab819ecee88e29e
Tx public key: f0933458401ae0082289d4fa59bb93e5a7250612e885f431147f93a8cf9def3b
Timestamp: 1731519131 Timestamp [UCT]: 2024-11-13 17:32:11 Age [y:d:h:m:s]: 00:175:10:40:27
Block: 1152962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125232 RingCT/type: yes/0
Extra: 01f0933458401ae0082289d4fa59bb93e5a7250612e885f431147f93a8cf9def3b0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbde0907f2ba7e90c2cb0e491c6babdfcd624afd0cfa7a59ed04d68c4222e2a4 0.600000000000 1638569 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": 1152972, "vin": [ { "gen": { "height": 1152962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbde0907f2ba7e90c2cb0e491c6babdfcd624afd0cfa7a59ed04d68c4222e2a4" } } ], "extra": [ 1, 240, 147, 52, 88, 64, 26, 224, 8, 34, 137, 212, 250, 89, 187, 147, 229, 167, 37, 6, 18, 232, 133, 244, 49, 20, 127, 147, 168, 207, 157, 239, 59, 2, 17, 0, 0, 0, 6, 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