Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12768f5a7df0e792b3dbe3590f7a933fe82becaa9722ca6f2a5b60c01e0e4ea4

Tx prefix hash: 8332e75e9c05afe6c28c88b6117fc85d1b5bea9a641e2e1f81e9cd1475c66a0f
Tx public key: 64ee98919cdc3749b665307c2e101544749abb04bc3059f38504e7ab4b21b04c
Timestamp: 1729024881 Timestamp [UCT]: 2024-10-15 20:41:21 Age [y:d:h:m:s]: 00:002:13:41:55
Block: 1132380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1842 RingCT/type: yes/0
Extra: 0164ee98919cdc3749b665307c2e101544749abb04bc3059f38504e7ab4b21b04c021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73ea5978e7f83ea948b72f6bff60ab8b001546b965e9f3c6f2c7b4fc320d2b91 0.600000000000 1615293 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": 1132390, "vin": [ { "gen": { "height": 1132380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73ea5978e7f83ea948b72f6bff60ab8b001546b965e9f3c6f2c7b4fc320d2b91" } } ], "extra": [ 1, 100, 238, 152, 145, 156, 220, 55, 73, 182, 101, 48, 124, 46, 16, 21, 68, 116, 154, 187, 4, 188, 48, 89, 243, 133, 4, 231, 171, 75, 33, 176, 76, 2, 17, 0, 0, 0, 3, 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