Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dce22b743b2a114876d245fa1ba67febd642c8d46a1ee603a03e9bac8408a2b

Tx prefix hash: 60a0720a5baff77c86e8f9000d6210646c13cb527193e4675e7404b9f89b60c8
Tx public key: 02d64136ab75699ec65617c952c9120667a493c9fd63e6a8ba8f364ab0a74fe8
Timestamp: 1718986515 Timestamp [UCT]: 2024-06-21 16:15:15 Age [y:d:h:m:s]: 01:152:19:47:37
Block: 1049135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367799 RingCT/type: yes/0
Extra: 0102d64136ab75699ec65617c952c9120667a493c9fd63e6a8ba8f364ab0a74fe80211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9133434d112317d494ff6892a4cc3104a698094e690a0c23c5ec629fbce7ec1e 0.600000000000 1519232 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": 1049145, "vin": [ { "gen": { "height": 1049135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9133434d112317d494ff6892a4cc3104a698094e690a0c23c5ec629fbce7ec1e" } } ], "extra": [ 1, 2, 214, 65, 54, 171, 117, 105, 158, 198, 86, 23, 201, 82, 201, 18, 6, 103, 164, 147, 201, 253, 99, 230, 168, 186, 143, 54, 74, 176, 167, 79, 232, 2, 17, 0, 0, 0, 3, 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