Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 420d55a39f3f4fa148008fbd9944bcd83c1b86ac0a74370ead3b0fb2fd29bbe5

Tx prefix hash: a626993457b38dd64bc17131e964b2569c4047a659acde60e510310361a54990
Tx public key: d9e4ae48a1f7b7831f3a5d69639f787480d2a12a1e9d9265046c4d54ad2fc954
Timestamp: 1745922016 Timestamp [UCT]: 2025-04-29 10:20:16 Age [y:d:h:m:s]: 00:207:17:01:22
Block: 1271953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146163 RingCT/type: yes/0
Extra: 01d9e4ae48a1f7b7831f3a5d69639f787480d2a12a1e9d9265046c4d54ad2fc9540211000000061f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb966e8a39074cc9ee385285b4f4b3a19a91d136cefd70dbd33d8ebcdb0b2d07 0.600000000000 1759224 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": 1271963, "vin": [ { "gen": { "height": 1271953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb966e8a39074cc9ee385285b4f4b3a19a91d136cefd70dbd33d8ebcdb0b2d07" } } ], "extra": [ 1, 217, 228, 174, 72, 161, 247, 183, 131, 31, 58, 93, 105, 99, 159, 120, 116, 128, 210, 161, 42, 30, 157, 146, 101, 4, 108, 77, 84, 173, 47, 201, 84, 2, 17, 0, 0, 0, 6, 31, 144, 81, 122, 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