Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c5b165774c397c8d15dce6b49661954822212a127827829ab5f807db41fdd38

Tx prefix hash: bdc647ffda4ce4bda988a09dc042c3762a38122a7cad9ea661a2489ef2f61e96
Tx public key: b20e3d6b7df5c003b25a0d6f0f0ede9f07057e1d15f100e35bcbf747fe7ab5ad
Timestamp: 1751746824 Timestamp [UCT]: 2025-07-05 20:20:24 Age [y:d:h:m:s]: 00:133:12:33:36
Block: 1319481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93785 RingCT/type: yes/0
Extra: 01b20e3d6b7df5c003b25a0d6f0f0ede9f07057e1d15f100e35bcbf747fe7ab5ad02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d86b6e53c17a6de0bd324d5c79f908dfaada04fad310d59426b82c005e872ede 0.600000000000 1807174 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": 1319491, "vin": [ { "gen": { "height": 1319481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d86b6e53c17a6de0bd324d5c79f908dfaada04fad310d59426b82c005e872ede" } } ], "extra": [ 1, 178, 14, 61, 107, 125, 245, 192, 3, 178, 90, 13, 111, 15, 14, 222, 159, 7, 5, 126, 29, 21, 241, 0, 227, 91, 203, 247, 71, 254, 122, 181, 173, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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