Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb1b16058bcfdce6367dda0f9045f0e81a2238b5739c1b6b2149c83625f893b1

Tx prefix hash: 8e55738ef1f07981ddb75a81e5269e26b5f0597d3339bc3e8c9d1784ef1ef0f2
Tx public key: ce08fc662f7fe049edfb728805ea3c614ed37404666a5ee0aafa3d4ecd762d4d
Timestamp: 1725587464 Timestamp [UCT]: 2024-09-06 01:51:04 Age [y:d:h:m:s]: 00:287:15:00:52
Block: 1103886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205280 RingCT/type: yes/0
Extra: 01ce08fc662f7fe049edfb728805ea3c614ed37404666a5ee0aafa3d4ecd762d4d021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 983b81ef9b9b2a9c6163ad49c6da3581de4591549f79d0044474cf28e4e135c9 0.600000000000 1580885 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": 1103896, "vin": [ { "gen": { "height": 1103886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "983b81ef9b9b2a9c6163ad49c6da3581de4591549f79d0044474cf28e4e135c9" } } ], "extra": [ 1, 206, 8, 252, 102, 47, 127, 224, 73, 237, 251, 114, 136, 5, 234, 60, 97, 78, 211, 116, 4, 102, 106, 94, 224, 170, 250, 61, 78, 205, 118, 45, 77, 2, 17, 0, 0, 0, 4, 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