Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f82a03fe6555dc1f4d823fa1bda703a987a255eaa984d004e442520db99aabd

Tx prefix hash: 23f94ab35705b779732947ae20083dd118dbfe81dcf445d2557b727734913e5f
Tx public key: a9e822c839ad13ea6e1bb13ebada1be1c22a583b33a89ad8c0f6ed5d0ca764c5
Timestamp: 1742621471 Timestamp [UCT]: 2025-03-22 05:31:11 Age [y:d:h:m:s]: 00:288:11:02:45
Block: 1244618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203980 RingCT/type: yes/0
Extra: 01a9e822c839ad13ea6e1bb13ebada1be1c22a583b33a89ad8c0f6ed5d0ca764c50211000000048368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e2d1171f317826da01f48f934523370814073f2760aa8cb95e89181e5b1ce6a 0.600000000000 1731609 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": 1244628, "vin": [ { "gen": { "height": 1244618 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e2d1171f317826da01f48f934523370814073f2760aa8cb95e89181e5b1ce6a" } } ], "extra": [ 1, 169, 232, 34, 200, 57, 173, 19, 234, 110, 27, 177, 62, 186, 218, 27, 225, 194, 42, 88, 59, 51, 168, 154, 216, 192, 246, 237, 93, 12, 167, 100, 197, 2, 17, 0, 0, 0, 4, 131, 104, 38, 109, 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