Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b86c23b232c5ec5ccad3299847fd67bfd6d6600477153425c6212c2d73b8f42a

Tx prefix hash: 52efc951cf2566f5f7e9b5e1d9bd0264d454595b2abb6fd6f432f3a392989096
Tx public key: 545d9155830c14aa2b19d280796be269e28fd99077990c306965baa3a21c47ed
Timestamp: 1726384407 Timestamp [UCT]: 2024-09-15 07:13:27 Age [y:d:h:m:s]: 00:241:23:00:46
Block: 1110480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172790 RingCT/type: yes/0
Extra: 01545d9155830c14aa2b19d280796be269e28fd99077990c306965baa3a21c47ed021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff1476fc3239305ea23ce134b46a24eac7928c5c7b0d9db8cb693b3d4efb7084 0.600000000000 1589103 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": 1110490, "vin": [ { "gen": { "height": 1110480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff1476fc3239305ea23ce134b46a24eac7928c5c7b0d9db8cb693b3d4efb7084" } } ], "extra": [ 1, 84, 93, 145, 85, 131, 12, 20, 170, 43, 25, 210, 128, 121, 107, 226, 105, 226, 143, 217, 144, 119, 153, 12, 48, 105, 101, 186, 163, 162, 28, 71, 237, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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