Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e60ed045c48c44c5f7382f253ac9d867ebc8a8355fc4715842b089f3ab9bf0e2

Tx prefix hash: 67b85313c4104c955c967830ff546bf430675d673b671bf30135ea86801c2679
Tx public key: 0163b80e041b8d666a1f2f5cf5f011f62579d06d9939c1fce2e02554aa85905e
Timestamp: 1710489656 Timestamp [UCT]: 2024-03-15 08:00:56 Age [y:d:h:m:s]: 01:073:11:24:39
Block: 978730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313517 RingCT/type: yes/0
Extra: 010163b80e041b8d666a1f2f5cf5f011f62579d06d9939c1fce2e02554aa85905e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49eef5ca8cb2f1c73b2befda9ac699d5ff82703856a4926c5709c6d822e8b467 0.600000000000 1438759 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": 978740, "vin": [ { "gen": { "height": 978730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49eef5ca8cb2f1c73b2befda9ac699d5ff82703856a4926c5709c6d822e8b467" } } ], "extra": [ 1, 1, 99, 184, 14, 4, 27, 141, 102, 106, 31, 47, 92, 245, 240, 17, 246, 37, 121, 208, 109, 153, 57, 193, 252, 226, 224, 37, 84, 170, 133, 144, 94, 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