Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6de479ed79fa1c03b8b457b1ef6a75c16c551494665098813b6315eb6f34d54

Tx prefix hash: 96f4d2cb00b5bb8c42521abe590363f9328a64c14ab6c7c716be942b90820e02
Tx public key: 61f960deb77ced9b5bf5ef8e4d3796582b753577a8d3b130c1fd260f9fc7cece
Timestamp: 1702694696 Timestamp [UCT]: 2023-12-16 02:44:56 Age [y:d:h:m:s]: 01:027:10:05:41
Block: 914088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280939 RingCT/type: yes/0
Extra: 0161f960deb77ced9b5bf5ef8e4d3796582b753577a8d3b130c1fd260f9fc7cece02110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ea17800d1794fe83f67aae42b6ac92ad1fef78b2d16f72fe860a863fad5d356 0.600000000000 1371370 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": 914098, "vin": [ { "gen": { "height": 914088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ea17800d1794fe83f67aae42b6ac92ad1fef78b2d16f72fe860a863fad5d356" } } ], "extra": [ 1, 97, 249, 96, 222, 183, 124, 237, 155, 91, 245, 239, 142, 77, 55, 150, 88, 43, 117, 53, 119, 168, 211, 177, 48, 193, 253, 38, 15, 159, 199, 206, 206, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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