Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fba486f1bdde493306d62380941175bb4948ad4a9e59347ad21e640f3f7a93e

Tx prefix hash: d0b41a78756545719eb845eb66eb72cc1caf4d202ab8fc890683f290f9f778ae
Tx public key: 5cee816dd676fc21b4c016b2c02c42af97af41e3a0aed99efba90d2e2f4cbf0d
Timestamp: 1703297374 Timestamp [UCT]: 2023-12-23 02:09:34 Age [y:d:h:m:s]: 01:103:10:02:45
Block: 919076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335038 RingCT/type: yes/0
Extra: 015cee816dd676fc21b4c016b2c02c42af97af41e3a0aed99efba90d2e2f4cbf0d02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9c2c05671579af2c536acce4cb894420b432d7abaa2ca9aa88c22e5a6df19c0 0.600000000000 1376740 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": 919086, "vin": [ { "gen": { "height": 919076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9c2c05671579af2c536acce4cb894420b432d7abaa2ca9aa88c22e5a6df19c0" } } ], "extra": [ 1, 92, 238, 129, 109, 214, 118, 252, 33, 180, 192, 22, 178, 192, 44, 66, 175, 151, 175, 65, 227, 160, 174, 217, 158, 251, 169, 13, 46, 47, 76, 191, 13, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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