Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf9c5761dc4e0e5d6a7ce0c2ae91a2039c435462617574d3685ef3718801b2e9

Tx prefix hash: 79fa4457ed67f4470c94d93eb8cea4cf01dd2eefc9e9ff7676888ec32bb4a8df
Tx public key: 6f9cb1a19e171e7cda01b8c3a99d8f6dd1b3e4bbd9d7cc21f2a664b316036767
Timestamp: 1765043159 Timestamp [UCT]: 2025-12-06 17:45:59 Age [y:d:h:m:s]: 00:016:18:41:08
Block: 1427852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12006 RingCT/type: yes/0
Extra: 016f9cb1a19e171e7cda01b8c3a99d8f6dd1b3e4bbd9d7cc21f2a664b31603676702110000000234af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b66fe875b10e93a7808a0b78cfd6016e5eb15e72083f7700c8c4b53ff2c633f 0.600000000000 1916559 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": 1427862, "vin": [ { "gen": { "height": 1427852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b66fe875b10e93a7808a0b78cfd6016e5eb15e72083f7700c8c4b53ff2c633f" } } ], "extra": [ 1, 111, 156, 177, 161, 158, 23, 30, 124, 218, 1, 184, 195, 169, 157, 143, 109, 209, 179, 228, 187, 217, 215, 204, 33, 242, 166, 100, 179, 22, 3, 103, 103, 2, 17, 0, 0, 0, 2, 52, 175, 49, 204, 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