Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ca9a5463f61dfa179ff215abbc3f8e2a6fd26f2188752d25ce80e1ffa96e14a

Tx prefix hash: a1b854f4351356042631140bca55b3505594ed4747fe2b6658070d8fa898a2df
Tx public key: bcf78d0de07d1f956bc4b04f71ba1f874d06d7f167c087ac0b5424310d5ee638
Timestamp: 1745247182 Timestamp [UCT]: 2025-04-21 14:53:02 Age [y:d:h:m:s]: 00:023:20:30:39
Block: 1266352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17070 RingCT/type: yes/0
Extra: 01bcf78d0de07d1f956bc4b04f71ba1f874d06d7f167c087ac0b5424310d5ee6380211000000026c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfa28bf5daa8e496b802908d6d39bdf150ae4d9a6b4d9f1eddaf2928f6ecd535 0.600000000000 1753573 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": 1266362, "vin": [ { "gen": { "height": 1266352 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfa28bf5daa8e496b802908d6d39bdf150ae4d9a6b4d9f1eddaf2928f6ecd535" } } ], "extra": [ 1, 188, 247, 141, 13, 224, 125, 31, 149, 107, 196, 176, 79, 113, 186, 31, 135, 77, 6, 215, 241, 103, 192, 135, 172, 11, 84, 36, 49, 13, 94, 230, 56, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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