Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 203b71f324a617df8d366d9f0776c97947da8c8efeb4fb808d6b8b837e994968

Tx prefix hash: b731afd673f09be908fc27f1c6e69f26a440e5e28023476a6a04fa22628d5aad
Tx public key: 291f4042704f6d42ab97284203bb4076ac62c51bafc1be2037cd809e27115518
Timestamp: 1741156989 Timestamp [UCT]: 2025-03-05 06:43:09 Age [y:d:h:m:s]: 00:306:13:02:49
Block: 1232495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216918 RingCT/type: yes/0
Extra: 01291f4042704f6d42ab97284203bb4076ac62c51bafc1be2037cd809e271155180211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75adf7b1a37399a7c7c7ae2ded90d8e0acd7a0052f11d60f598b9abc24d7d2bb 0.600000000000 1719408 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": 1232505, "vin": [ { "gen": { "height": 1232495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75adf7b1a37399a7c7c7ae2ded90d8e0acd7a0052f11d60f598b9abc24d7d2bb" } } ], "extra": [ 1, 41, 31, 64, 66, 112, 79, 109, 66, 171, 151, 40, 66, 3, 187, 64, 118, 172, 98, 197, 27, 175, 193, 190, 32, 55, 205, 128, 158, 39, 17, 85, 24, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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