Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b5cfe59d30a009a85c8818ffe4099b60c99735c1eb4922701f9a648f8642997

Tx prefix hash: 27a85177cc8137783e15917820a47b0e669a7c510974498170f35a2c29c52f27
Tx public key: 19f805df01bfab027bcb3a818a8a0152e07b701245125e6cbb82fa8d429cb3ea
Timestamp: 1579015894 Timestamp [UCT]: 2020-01-14 15:31:34 Age [y:d:h:m:s]: 05:027:08:08:55
Block: 45397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1169725 RingCT/type: yes/0
Extra: 0119f805df01bfab027bcb3a818a8a0152e07b701245125e6cbb82fa8d429cb3ea021100000101391a8d0e000000000000000000

1 output(s) for total of 434.091951377000 dcy

stealth address amount amount idx
00: 60ea6a9f92d30a28b9958679ef9ccb09b5e14dbba35ce074319f889c28c1458f 434.091951377000 82927 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": 45407, "vin": [ { "gen": { "height": 45397 } } ], "vout": [ { "amount": 434091951377, "target": { "key": "60ea6a9f92d30a28b9958679ef9ccb09b5e14dbba35ce074319f889c28c1458f" } } ], "extra": [ 1, 25, 248, 5, 223, 1, 191, 171, 2, 123, 203, 58, 129, 138, 138, 1, 82, 224, 123, 112, 18, 69, 18, 94, 108, 187, 130, 250, 141, 66, 156, 179, 234, 2, 17, 0, 0, 1, 1, 57, 26, 141, 14, 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