Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 877969fa01a979b9cdc9a9b8ff4e6c99cfa70afb1f8b453051d5b7f1e0a7cb24

Tx prefix hash: 8aa080b447bfd91e401f9880829494e39f6a2142b0eaf7d4658a2e94eeab2220
Tx public key: 8d9ecc54b8a93cd6f3858efeba55c44ba160f0d379fcb6af0fa69da34b830a49
Timestamp: 1730924386 Timestamp [UCT]: 2024-11-06 20:19:46 Age [y:d:h:m:s]: 00:000:12:19:17
Block: 1148039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372 RingCT/type: yes/0
Extra: 018d9ecc54b8a93cd6f3858efeba55c44ba160f0d379fcb6af0fa69da34b830a490211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b1c4cf36d5e2ec5f38be63399e6e1a353d6bebf19c6f29daa2c8191082b8f65 0.600000000000 1632786 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": 1148049, "vin": [ { "gen": { "height": 1148039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b1c4cf36d5e2ec5f38be63399e6e1a353d6bebf19c6f29daa2c8191082b8f65" } } ], "extra": [ 1, 141, 158, 204, 84, 184, 169, 60, 214, 243, 133, 142, 254, 186, 85, 196, 75, 161, 96, 240, 211, 121, 252, 182, 175, 15, 166, 157, 163, 75, 131, 10, 73, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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