Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b3e3546b671bdcfec62ecb258ff68bd424e93ae66ca10d4f26524e09d1e896b

Tx prefix hash: e77fda66a370c0d1d9c3687d572a72447bd73b4f3c0f0381ac8c5dc2e0a32bba
Tx public key: e9c9e0dc545839418ea225c3c410c026fb498752dd88acf229ce8d074dc6a4c0
Timestamp: 1711803683 Timestamp [UCT]: 2024-03-30 13:01:23 Age [y:d:h:m:s]: 01:063:07:59:24
Block: 989627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306244 RingCT/type: yes/0
Extra: 01e9c9e0dc545839418ea225c3c410c026fb498752dd88acf229ce8d074dc6a4c00211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00017a8aea6406c037bc0d21c1761532f7b3e288855c2d9d0e3b90d66ccbd0e5 0.600000000000 1449930 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": 989637, "vin": [ { "gen": { "height": 989627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00017a8aea6406c037bc0d21c1761532f7b3e288855c2d9d0e3b90d66ccbd0e5" } } ], "extra": [ 1, 233, 201, 224, 220, 84, 88, 57, 65, 142, 162, 37, 195, 196, 16, 192, 38, 251, 73, 135, 82, 221, 136, 172, 242, 41, 206, 141, 7, 77, 198, 164, 192, 2, 17, 0, 0, 0, 1, 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