Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67f5b34c933ecf98ecc20be98925f142a371810629eed7a2bbc3926c3e15fec3

Tx prefix hash: 820020ce4b3c244bd30f15850dc5ac2f92781f8da7d6f0710495f484e3c9ad0a
Tx public key: c7a1cd89e618641ac6403f0e1b10a564f07537464035c38a633fa2083fd5ae7c
Timestamp: 1715077611 Timestamp [UCT]: 2024-05-07 10:26:51 Age [y:d:h:m:s]: 01:024:02:54:20
Block: 1016755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278188 RingCT/type: yes/0
Extra: 01c7a1cd89e618641ac6403f0e1b10a564f07537464035c38a633fa2083fd5ae7c0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eaa3ec0032c746841f1d192d944702b4e870308d1d324905914d68994123b241 0.600000000000 1480428 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": 1016765, "vin": [ { "gen": { "height": 1016755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eaa3ec0032c746841f1d192d944702b4e870308d1d324905914d68994123b241" } } ], "extra": [ 1, 199, 161, 205, 137, 230, 24, 100, 26, 198, 64, 63, 14, 27, 16, 165, 100, 240, 117, 55, 70, 64, 53, 195, 138, 99, 63, 162, 8, 63, 213, 174, 124, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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