Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55bdde1fab7e4d6d474790d6f87165b6f182a742e8cb5f425d078cb0558e4185

Tx prefix hash: 58155343bc27933ab339478b3412534e19e7f8f67f4ff7a90b239cb07f6b9e0c
Tx public key: b180d8fcdfdcef7dcfc41814d19de250ecf40720bb6f1aa354ef70ec1ab51ba2
Timestamp: 1717244836 Timestamp [UCT]: 2024-06-01 12:27:16 Age [y:d:h:m:s]: 00:306:10:53:27
Block: 1034724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219005 RingCT/type: yes/0
Extra: 01b180d8fcdfdcef7dcfc41814d19de250ecf40720bb6f1aa354ef70ec1ab51ba20211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ef6e12f679e576b2d0ee11d8bc25dd4a69dc397a6ef72980b5ec087496978a1 0.600000000000 1503243 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": 1034734, "vin": [ { "gen": { "height": 1034724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ef6e12f679e576b2d0ee11d8bc25dd4a69dc397a6ef72980b5ec087496978a1" } } ], "extra": [ 1, 177, 128, 216, 252, 223, 220, 239, 125, 207, 196, 24, 20, 209, 157, 226, 80, 236, 244, 7, 32, 187, 111, 26, 163, 84, 239, 112, 236, 26, 181, 27, 162, 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