Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2161094fba4adeb1a2d63218ffa03d9874a54141d63e220260c527ac87b2f3fa

Tx prefix hash: c2dfce4d0e3a3f05a3a2d2aa410b6d08c339a1e975bd16531c16025f67f36e62
Tx public key: 445939a58e9374b3f74bc3e5d2ba65c6ca5c589cf626fca4b969325fb3746d5a
Timestamp: 1722513188 Timestamp [UCT]: 2024-08-01 11:53:08 Age [y:d:h:m:s]: 00:279:09:23:58
Block: 1078386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199604 RingCT/type: yes/0
Extra: 01445939a58e9374b3f74bc3e5d2ba65c6ca5c589cf626fca4b969325fb3746d5a021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17671cc949193268865750e898ebc7bab07fe9105beb1a0c6af401ec4f770fdb 0.600000000000 1550963 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": 1078396, "vin": [ { "gen": { "height": 1078386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17671cc949193268865750e898ebc7bab07fe9105beb1a0c6af401ec4f770fdb" } } ], "extra": [ 1, 68, 89, 57, 165, 142, 147, 116, 179, 247, 75, 195, 229, 210, 186, 101, 198, 202, 92, 88, 156, 246, 38, 252, 164, 185, 105, 50, 95, 179, 116, 109, 90, 2, 17, 0, 0, 0, 6, 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