Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd7c20395d2c50044e0681dfbdadfe03bdfe4f5679ebdffe37dd8b98c894570d

Tx prefix hash: e73bc5a9e8cd88b1277a491e516a8925e0fd66f20b59aaf732eff98487841e2f
Tx public key: cf013d08c4df0c162953a0e52f1195e6c305945c2090e1f176af2edfa6407467
Timestamp: 1716120844 Timestamp [UCT]: 2024-05-19 12:14:04 Age [y:d:h:m:s]: 00:281:05:42:29
Block: 1025400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200979 RingCT/type: yes/0
Extra: 01cf013d08c4df0c162953a0e52f1195e6c305945c2090e1f176af2edfa640746702110000000652d47e94000000000000000000

1 output(s) for total of 0.615590000000 dcy

stealth address amount amount idx
00: 7ee197c6df5bac1a07d34440d1436c113af363acb0f4689e9c61a431d4badac8 0.615590000000 1491873 of 0

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": 1025410, "vin": [ { "gen": { "height": 1025400 } } ], "vout": [ { "amount": 615590000, "target": { "key": "7ee197c6df5bac1a07d34440d1436c113af363acb0f4689e9c61a431d4badac8" } } ], "extra": [ 1, 207, 1, 61, 8, 196, 223, 12, 22, 41, 83, 160, 229, 47, 17, 149, 230, 195, 5, 148, 92, 32, 144, 225, 241, 118, 175, 46, 223, 166, 64, 116, 103, 2, 17, 0, 0, 0, 6, 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