Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b85a12e1579f4c0f7eac7d922e3a0ce8ca4ce969de7bee44f4d8a695d2be8eb4

Tx prefix hash: 4c7bd22ae1370d990849726cf42fb78cdd924ecaeb1b932ea135cb109e659922
Tx public key: 20372c7b241c2f1643666141280c49bdf74a78682ebac9d67c179d82990b3721
Timestamp: 1694880478 Timestamp [UCT]: 2023-09-16 16:07:58 Age [y:d:h:m:s]: 01:104:00:14:42
Block: 849486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335636 RingCT/type: yes/0
Extra: 0120372c7b241c2f1643666141280c49bdf74a78682ebac9d67c179d82990b372102110000000475e3f0e9000000000000000000

1 output(s) for total of 0.940373324000 dcy

stealth address amount amount idx
00: 69d58ff5cbe407281fde1615d7ee715aa5c80bc21d40aabd0c9c1348c511ab42 0.940373324000 1303154 of 0

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": 849496, "vin": [ { "gen": { "height": 849486 } } ], "vout": [ { "amount": 940373324, "target": { "key": "69d58ff5cbe407281fde1615d7ee715aa5c80bc21d40aabd0c9c1348c511ab42" } } ], "extra": [ 1, 32, 55, 44, 123, 36, 28, 47, 22, 67, 102, 97, 65, 40, 12, 73, 189, 247, 74, 120, 104, 46, 186, 201, 214, 124, 23, 157, 130, 153, 11, 55, 33, 2, 17, 0, 0, 0, 4, 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