Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c720b14f798fb92cd7f46b0e1e8fc304e9848b4d12002523051e8c77b2441453

Tx prefix hash: f9afa860c9202b20c34f2a03199eb2474dcdd0e260428434e641161833416a3a
Tx public key: 0e4026b7ea60b33a64ef723d29fc29b6b511bd95114463fbbef5cad8a7c2d88d
Timestamp: 1727315015 Timestamp [UCT]: 2024-09-26 01:43:35 Age [y:d:h:m:s]: 00:197:06:52:59
Block: 1118201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140818 RingCT/type: yes/0
Extra: 010e4026b7ea60b33a64ef723d29fc29b6b511bd95114463fbbef5cad8a7c2d88d021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a9dafdf1f9e3dd772ca269f64c6d76c49ddd810164192537de6bcfdce2e6e35 0.600000000000 1599312 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": 1118211, "vin": [ { "gen": { "height": 1118201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a9dafdf1f9e3dd772ca269f64c6d76c49ddd810164192537de6bcfdce2e6e35" } } ], "extra": [ 1, 14, 64, 38, 183, 234, 96, 179, 58, 100, 239, 114, 61, 41, 252, 41, 182, 181, 17, 189, 149, 17, 68, 99, 251, 190, 245, 202, 216, 167, 194, 216, 141, 2, 17, 0, 0, 0, 1, 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