Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68a0c615ed1beba2b0dbe9fd9aac66a2b9fa2c36ec2c1f5d6442ec807c493d48

Tx prefix hash: dd8f260d850b3b0233d90c98b7741990ac4e835fcc8b9521e3c9c57fa438247d
Tx public key: 3ba4ed7e72f6c38e515ea407cf1840296a043e2de06f52e41927c50d63ddf050
Timestamp: 1701132076 Timestamp [UCT]: 2023-11-28 00:41:16 Age [y:d:h:m:s]: 01:168:08:40:42
Block: 901137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381514 RingCT/type: yes/0
Extra: 013ba4ed7e72f6c38e515ea407cf1840296a043e2de06f52e41927c50d63ddf0500211000000054b8f5122000000000000000000

1 output(s) for total of 0.634101851000 dcy

stealth address amount amount idx
00: fd9b76c1d17ddd925ccebe3b9376a4d4e260b4c43b652b89dd75254e037e9ea1 0.634101851000 1357668 of 0

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": 901147, "vin": [ { "gen": { "height": 901137 } } ], "vout": [ { "amount": 634101851, "target": { "key": "fd9b76c1d17ddd925ccebe3b9376a4d4e260b4c43b652b89dd75254e037e9ea1" } } ], "extra": [ 1, 59, 164, 237, 126, 114, 246, 195, 142, 81, 94, 164, 7, 207, 24, 64, 41, 106, 4, 62, 45, 224, 111, 82, 228, 25, 39, 197, 13, 99, 221, 240, 80, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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