Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b5053b205af27cdcd1a624e4237d75abf9dd5dcda48b63e332718c947c39799

Tx prefix hash: 1cec1b1123844b838a36cf93c2010c4bc91bf1beae07812d6ad3d334b9645b1a
Tx public key: 0a481684d3d0fafd775db8bf642f3aad3e5da4e88f17cf19af6423df4a5fe1d6
Timestamp: 1723983953 Timestamp [UCT]: 2024-08-18 12:25:53 Age [y:d:h:m:s]: 00:145:06:11:54
Block: 1090587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103907 RingCT/type: yes/0
Extra: 010a481684d3d0fafd775db8bf642f3aad3e5da4e88f17cf19af6423df4a5fe1d602110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 936859d9ae78fe2496fe8fa2ace921b45c308672748b6ee74fe091a2576eb432 0.600000000000 1565210 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": 1090597, "vin": [ { "gen": { "height": 1090587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "936859d9ae78fe2496fe8fa2ace921b45c308672748b6ee74fe091a2576eb432" } } ], "extra": [ 1, 10, 72, 22, 132, 211, 208, 250, 253, 119, 93, 184, 191, 100, 47, 58, 173, 62, 93, 164, 232, 143, 23, 207, 25, 175, 100, 35, 223, 74, 95, 225, 214, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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