Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3db1e01c24082b07376945b2d3efbc9481ffbe1bef98e2ffa969426b570fefb

Tx prefix hash: 45dd62e66ce20d9955eee8e8b004a89a617ecf06860ff3c8638a6947799b62ea
Tx public key: 9d4382a6e9acdf193b0af29cd5a7a305011948f4852f38ff2bc5d50c00c922dc
Timestamp: 1731070100 Timestamp [UCT]: 2024-11-08 12:48:20 Age [y:d:h:m:s]: 00:197:09:05:10
Block: 1149253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140919 RingCT/type: yes/0
Extra: 019d4382a6e9acdf193b0af29cd5a7a305011948f4852f38ff2bc5d50c00c922dc0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b858d31f2d407d23ac735a7bc7ed3b9c98bd5819144ac49ad36aa167328826e 0.600000000000 1634292 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": 1149263, "vin": [ { "gen": { "height": 1149253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b858d31f2d407d23ac735a7bc7ed3b9c98bd5819144ac49ad36aa167328826e" } } ], "extra": [ 1, 157, 67, 130, 166, 233, 172, 223, 25, 59, 10, 242, 156, 213, 167, 163, 5, 1, 25, 72, 244, 133, 47, 56, 255, 43, 197, 213, 12, 0, 201, 34, 220, 2, 17, 0, 0, 0, 7, 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