Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee4df02e33f2c9c26a364ae73ce32a09dabc7659a4aa61ca5e0f5922466ff930

Tx prefix hash: 73e6969ece497e3afeac9dd79859801e158cc917bc64a01d3f06741db892e4a3
Tx public key: e02f4dc158e39ef8f07575a1660463eaff00af2995c4bf9e9ae75174fabf925e
Timestamp: 1700982211 Timestamp [UCT]: 2023-11-26 07:03:31 Age [y:d:h:m:s]: 01:360:18:35:12
Block: 899879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516739 RingCT/type: yes/0
Extra: 01e02f4dc158e39ef8f07575a1660463eaff00af2995c4bf9e9ae75174fabf925e021100000001faf35c9c000000000000000000

1 output(s) for total of 0.640217143000 dcy

stealth address amount amount idx
00: 478246735165aae2d9bddeeb5d18c5aaf745c255ab5ea3187d46820bb33c5849 0.640217143000 1356348 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": 899889, "vin": [ { "gen": { "height": 899879 } } ], "vout": [ { "amount": 640217143, "target": { "key": "478246735165aae2d9bddeeb5d18c5aaf745c255ab5ea3187d46820bb33c5849" } } ], "extra": [ 1, 224, 47, 77, 193, 88, 227, 158, 248, 240, 117, 117, 161, 102, 4, 99, 234, 255, 0, 175, 41, 149, 196, 191, 158, 154, 231, 81, 116, 250, 191, 146, 94, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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