Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed86179828d978319dcd2b948861a4a0f55f8f3f10852827bbed67bf95476f8f

Tx prefix hash: 8d113df277705c07737e8a3797665d97d9d377be9053b5858a3e10fab701e02d
Tx public key: e0b124fcab312864980f2facf7632dc5ad4b688d6d53c49e5ebc90d11c4377e6
Timestamp: 1698410694 Timestamp [UCT]: 2023-10-27 12:44:54 Age [y:d:h:m:s]: 01:153:06:59:59
Block: 878789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370545 RingCT/type: yes/0
Extra: 01e0b124fcab312864980f2facf7632dc5ad4b688d6d53c49e5ebc90d11c4377e6021100000004faf35c9c000000000000000000

1 output(s) for total of 0.751981670000 dcy

stealth address amount amount idx
00: e189dc6ade7c9bbad1e5bff10495813f6eac1945fa62d185c42504e97056e9ab 0.751981670000 1334267 of 0

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": 878799, "vin": [ { "gen": { "height": 878789 } } ], "vout": [ { "amount": 751981670, "target": { "key": "e189dc6ade7c9bbad1e5bff10495813f6eac1945fa62d185c42504e97056e9ab" } } ], "extra": [ 1, 224, 177, 36, 252, 171, 49, 40, 100, 152, 15, 47, 172, 247, 99, 45, 197, 173, 75, 104, 141, 109, 83, 196, 158, 94, 188, 144, 209, 28, 67, 119, 230, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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