Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3dda4a4c971bdf3361a38013fa8daff429c1b7365ee2d17cce57333fa912f29

Tx prefix hash: 3f131680984cdbd364e38332179e3ca8c5894ae63e9c92469a2212b3784dabd9
Tx public key: 6aa1a705efa3b82ddc1cafb1de36a21508ba39a95b6cc6ea4b7fa7a1550c6a0b
Timestamp: 1753251832 Timestamp [UCT]: 2025-07-23 06:23:52 Age [y:d:h:m:s]: 00:120:21:41:12
Block: 1331474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85219 RingCT/type: yes/0
Extra: 016aa1a705efa3b82ddc1cafb1de36a21508ba39a95b6cc6ea4b7fa7a1550c6a0b021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed3b0887cc3eb32b5d1a55e2fca28bc1de780c27d80e8485fc4bfc47d53c2d34 0.600000000000 1819269 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": 1331484, "vin": [ { "gen": { "height": 1331474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed3b0887cc3eb32b5d1a55e2fca28bc1de780c27d80e8485fc4bfc47d53c2d34" } } ], "extra": [ 1, 106, 161, 167, 5, 239, 163, 184, 45, 220, 28, 175, 177, 222, 54, 162, 21, 8, 186, 57, 169, 91, 108, 198, 234, 75, 127, 167, 161, 85, 12, 106, 11, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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