Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b92bb888ea711a9cb5938bcd44101acfce347854d5323621f7f2cbbb9d4c6066

Tx prefix hash: 03a26c40537ccc0d09843261cb50ca14b85f5d66f804092883fc30049d9875ab
Tx public key: 28b9bf043e622c4067126d593dafc9e3ecb5f1d6d3caeb6ffd23250f9bf802d0
Timestamp: 1672842975 Timestamp [UCT]: 2023-01-04 14:36:15 Age [y:d:h:m:s]: 02:101:07:21:20
Block: 667466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594088 RingCT/type: yes/0
Extra: 0128b9bf043e622c4067126d593dafc9e3ecb5f1d6d3caeb6ffd23250f9bf802d002110000000ce6d27f9c000000000000000000

1 output(s) for total of 3.770578828000 dcy

stealth address amount amount idx
00: 51cbb156aeb04d30da5c82396dbc2a56f22756425071070d2548c9344a841153 3.770578828000 1108653 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": 667476, "vin": [ { "gen": { "height": 667466 } } ], "vout": [ { "amount": 3770578828, "target": { "key": "51cbb156aeb04d30da5c82396dbc2a56f22756425071070d2548c9344a841153" } } ], "extra": [ 1, 40, 185, 191, 4, 62, 98, 44, 64, 103, 18, 109, 89, 61, 175, 201, 227, 236, 181, 241, 214, 211, 202, 235, 111, 253, 35, 37, 15, 155, 248, 2, 208, 2, 17, 0, 0, 0, 12, 230, 210, 127, 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