Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f0adcb59717b54f15146b1b20290973866c7dc00c2802ae1ad09d4ed8ae1acd

Tx prefix hash: 21c06e874d4ed5e6816abb462fbdcfc07170f54dcbe0b13188e1a1023137bb9e
Tx public key: 007c90a4af1d711da2ba1671b0852fcf673789eaf08eb94a8ca2e2c92042b227
Timestamp: 1703653143 Timestamp [UCT]: 2023-12-27 04:59:03 Age [y:d:h:m:s]: 01:317:02:58:37
Block: 922025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485490 RingCT/type: yes/0
Extra: 01007c90a4af1d711da2ba1671b0852fcf673789eaf08eb94a8ca2e2c92042b22702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee8d4185272de9d1fcacac5c9fa5ffd16f3765a3be52268e7d3ec8ce3f123ddc 0.600000000000 1379719 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": 922035, "vin": [ { "gen": { "height": 922025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee8d4185272de9d1fcacac5c9fa5ffd16f3765a3be52268e7d3ec8ce3f123ddc" } } ], "extra": [ 1, 0, 124, 144, 164, 175, 29, 113, 29, 162, 186, 22, 113, 176, 133, 47, 207, 103, 55, 137, 234, 240, 142, 185, 74, 140, 162, 226, 201, 32, 66, 178, 39, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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