Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c369538313e41377254374582f6f47278b629bcee1a13cd4bdd13dc979382a7

Tx prefix hash: 45690440ea1fde70305c1ef174494aa70e3c98a7ed994e801691b6a5d9c12c68
Tx public key: a2278d72e2a576d7c9b9acee0352dccee3b2adc513578019e11b399bec19d6bd
Timestamp: 1751746639 Timestamp [UCT]: 2025-07-05 20:17:19 Age [y:d:h:m:s]: 00:135:02:46:59
Block: 1319478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94926 RingCT/type: yes/0
Extra: 01a2278d72e2a576d7c9b9acee0352dccee3b2adc513578019e11b399bec19d6bd02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1c0324e7c9411030126c417253281a164829bbd7b8110cd0485d4f2bdf4cd66 0.600000000000 1807171 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": 1319488, "vin": [ { "gen": { "height": 1319478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1c0324e7c9411030126c417253281a164829bbd7b8110cd0485d4f2bdf4cd66" } } ], "extra": [ 1, 162, 39, 141, 114, 226, 165, 118, 215, 201, 185, 172, 238, 3, 82, 220, 206, 227, 178, 173, 197, 19, 87, 128, 25, 225, 27, 57, 155, 236, 25, 214, 189, 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