Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c650e1a32accd0e0bd3c84688c47fd36b51e928c3c8b3a21d1fd24b450480d27

Tx prefix hash: e465b8525969cf01d5009ec4dc8f09ac7ad2be582e53ea577bad1364c8e114ed
Tx public key: b424bbd6657e3b9faa5813f5f1b3daaf70a33581fba0d402f88add080a983497
Timestamp: 1763256844 Timestamp [UCT]: 2025-11-16 01:34:04 Age [y:d:h:m:s]: 00:053:18:09:02
Block: 1413045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38506 RingCT/type: yes/0
Extra: 01b424bbd6657e3b9faa5813f5f1b3daaf70a33581fba0d402f88add080a983497021100000005da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab84082b206314026b4a89761f39bd7dc852e83c769645342e6c5828ad4fcff1 0.600000000000 1901522 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": 1413055, "vin": [ { "gen": { "height": 1413045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab84082b206314026b4a89761f39bd7dc852e83c769645342e6c5828ad4fcff1" } } ], "extra": [ 1, 180, 36, 187, 214, 101, 126, 59, 159, 170, 88, 19, 245, 241, 179, 218, 175, 112, 163, 53, 129, 251, 160, 212, 2, 248, 138, 221, 8, 10, 152, 52, 151, 2, 17, 0, 0, 0, 5, 218, 85, 72, 72, 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