Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bf3badb7a0b9656f0e1066a56856676f08c5222e9a7b63f7183b90b1ac50535

Tx prefix hash: f93b8b383b09bb43bb75294e3c89fbda8cb84e40cadd52456fb56a3afeded062
Tx public key: 39c2b7375ffcdab9e7f000d64fff1b3c190ba6ec7976d148f5039081d799004f
Timestamp: 1733973355 Timestamp [UCT]: 2024-12-12 03:15:55 Age [y:d:h:m:s]: 00:109:09:27:49
Block: 1173313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77961 RingCT/type: yes/0
Extra: 0139c2b7375ffcdab9e7f000d64fff1b3c190ba6ec7976d148f5039081d799004f021100000001a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6acf338177e6f5a42c68c6e5ebf08b10368b57b98ffd9c8c2cff2ef5f83e6810 0.600000000000 1659322 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": 1173323, "vin": [ { "gen": { "height": 1173313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6acf338177e6f5a42c68c6e5ebf08b10368b57b98ffd9c8c2cff2ef5f83e6810" } } ], "extra": [ 1, 57, 194, 183, 55, 95, 252, 218, 185, 231, 240, 0, 214, 79, 255, 27, 60, 25, 11, 166, 236, 121, 118, 209, 72, 245, 3, 144, 129, 215, 153, 0, 79, 2, 17, 0, 0, 0, 1, 162, 215, 95, 68, 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