Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee7db532bfa1abc6526b073d604dcb53ccd9aefd5694060d48aee72849284e02

Tx prefix hash: 011c96b17575fd64b0be874f6816450a89b61105654e2d01eb1e26bcd5f383aa
Tx public key: 6a6ac978381c176b4e5283d9adeabad90d4dcfef92b87c473fb040bb05af6054
Timestamp: 1722562156 Timestamp [UCT]: 2024-08-02 01:29:16 Age [y:d:h:m:s]: 00:089:19:52:37
Block: 1078795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64272 RingCT/type: yes/0
Extra: 016a6ac978381c176b4e5283d9adeabad90d4dcfef92b87c473fb040bb05af605402110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f97b4d6c6a6a0bff037a78b4f3765a55f9707ac9d0d148ab42b243a68a705bd3 0.600000000000 1551478 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": 1078805, "vin": [ { "gen": { "height": 1078795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f97b4d6c6a6a0bff037a78b4f3765a55f9707ac9d0d148ab42b243a68a705bd3" } } ], "extra": [ 1, 106, 106, 201, 120, 56, 28, 23, 107, 78, 82, 131, 217, 173, 234, 186, 217, 13, 77, 207, 239, 146, 184, 124, 71, 63, 176, 64, 187, 5, 175, 96, 84, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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