Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 912ba330adbf9b7782ecf6ae6984ab41b407555b22a691639de6661de375e5c5

Tx prefix hash: fbde1261cf1dd1a272deb44704032f0a29e9699d53e3358127b2b11dcb156c35
Tx public key: 97a0fac67f6fec65015d4e7ded7f85830d31bbfbb95a114ee5a1e6989e5898b7
Timestamp: 1699270478 Timestamp [UCT]: 2023-11-06 11:34:38 Age [y:d:h:m:s]: 01:099:06:54:14
Block: 885695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332144 RingCT/type: yes/0
Extra: 0197a0fac67f6fec65015d4e7ded7f85830d31bbfbb95a114ee5a1e6989e5898b70211000000014b8f5122000000000000000000

1 output(s) for total of 0.713386358000 dcy

stealth address amount amount idx
00: a589e06f84e875c19b0d43bd214e9c4f4d9c042e608c57a4940b2ce0b8e2cc0e 0.713386358000 1341478 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": 885705, "vin": [ { "gen": { "height": 885695 } } ], "vout": [ { "amount": 713386358, "target": { "key": "a589e06f84e875c19b0d43bd214e9c4f4d9c042e608c57a4940b2ce0b8e2cc0e" } } ], "extra": [ 1, 151, 160, 250, 198, 127, 111, 236, 101, 1, 93, 78, 125, 237, 127, 133, 131, 13, 49, 187, 251, 185, 90, 17, 78, 229, 161, 230, 152, 158, 88, 152, 183, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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