Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 897b1d7f476c3d920143a16ce55b5691faad88b1624e8150cbe5e807b3c75ae2

Tx prefix hash: 9258efa66bd0cddcf8cf0fd9aabea2d292ceb64e2179fcb893ad130fc9c3aa20
Tx public key: 33f66ea8dcf4683b9138357ef7059580f7d68f718a6f321851faaebc79994b76
Timestamp: 1695918792 Timestamp [UCT]: 2023-09-28 16:33:12 Age [y:d:h:m:s]: 01:242:02:23:42
Block: 858115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434115 RingCT/type: yes/0
Extra: 0133f66ea8dcf4683b9138357ef7059580f7d68f718a6f321851faaebc79994b7602110000000233af99f4000000000000000000

1 output(s) for total of 0.880458376000 dcy

stealth address amount amount idx
00: b4310b31de930d1f2617a33d8cf8793f99809388fec2a293577f824ee1f0e0cc 0.880458376000 1312279 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": 858125, "vin": [ { "gen": { "height": 858115 } } ], "vout": [ { "amount": 880458376, "target": { "key": "b4310b31de930d1f2617a33d8cf8793f99809388fec2a293577f824ee1f0e0cc" } } ], "extra": [ 1, 51, 246, 110, 168, 220, 244, 104, 59, 145, 56, 53, 126, 247, 5, 149, 128, 247, 214, 143, 113, 138, 111, 50, 24, 81, 250, 174, 188, 121, 153, 75, 118, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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