Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a1270add5ad5caaacb88fceeb04bf1d459f26c9fe32210df790f6ba5632b9a4

Tx prefix hash: a511a54a40bb5e3f0664aea21839ac7ee68ee8e48b30451673bc6de3f6dab9fe
Tx public key: cb8edee4bccd76ac0c7ee5c772f147119acb17e68a5647b08e8d218a3cb97cad
Timestamp: 1736952039 Timestamp [UCT]: 2025-01-15 14:40:39 Age [y:d:h:m:s]: 00:153:23:16:37
Block: 1197946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109748 RingCT/type: yes/0
Extra: 01cb8edee4bccd76ac0c7ee5c772f147119acb17e68a5647b08e8d218a3cb97cad021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 725e41d32af193b2317b8e138e2308b3a201111e7bb2e17bdf126452452b89f5 0.600000000000 1684563 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": 1197956, "vin": [ { "gen": { "height": 1197946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "725e41d32af193b2317b8e138e2308b3a201111e7bb2e17bdf126452452b89f5" } } ], "extra": [ 1, 203, 142, 222, 228, 188, 205, 118, 172, 12, 126, 229, 199, 114, 241, 71, 17, 154, 203, 23, 230, 138, 86, 71, 176, 142, 141, 33, 138, 60, 185, 124, 173, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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