Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4595edcec369e2dcf59b58e158c0110bb21375ff6cb961c62e5bf54c0b9d516c

Tx prefix hash: 41d566f3225d79b9c0974f23aa2676c1a24e5983e62545b48d88a61b96ee05d3
Tx public key: 4f74464c5388cef54587df05904091c0bf4fd445af375343d190850dc5bb99f0
Timestamp: 1732595916 Timestamp [UCT]: 2024-11-26 04:38:36 Age [y:d:h:m:s]: 00:136:02:56:23
Block: 1161881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97108 RingCT/type: yes/0
Extra: 014f74464c5388cef54587df05904091c0bf4fd445af375343d190850dc5bb99f0021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08cc6ff43d0c4d76354c960a7fd1f5dbad8a1e25866cd94d703ecfa21e6d0b84 0.600000000000 1647536 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": 1161891, "vin": [ { "gen": { "height": 1161881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08cc6ff43d0c4d76354c960a7fd1f5dbad8a1e25866cd94d703ecfa21e6d0b84" } } ], "extra": [ 1, 79, 116, 70, 76, 83, 136, 206, 245, 69, 135, 223, 5, 144, 64, 145, 192, 191, 79, 212, 69, 175, 55, 83, 67, 209, 144, 133, 13, 197, 187, 153, 240, 2, 17, 0, 0, 0, 2, 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