Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b191399077bf005e375c8593dca9d19683294dc563b2d48e0723cfafd121045e

Tx prefix hash: 03094eb4fec9c92af810a93b68dfea4be9a38fd6b4a053785e371497e56392fb
Tx public key: 2ea62c5795aff30f4a3c90ca97ee6356df4f41a7ec1ab5d1a9c58ef077c30eb5
Timestamp: 1722284194 Timestamp [UCT]: 2024-07-29 20:16:34 Age [y:d:h:m:s]: 00:324:04:28:00
Block: 1076494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231514 RingCT/type: yes/0
Extra: 012ea62c5795aff30f4a3c90ca97ee6356df4f41a7ec1ab5d1a9c58ef077c30eb502110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7809fb649ff014087f762e3f93a7f3a28e226db01d1088ec2ebb954de28edbb5 0.600000000000 1549031 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": 1076504, "vin": [ { "gen": { "height": 1076494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7809fb649ff014087f762e3f93a7f3a28e226db01d1088ec2ebb954de28edbb5" } } ], "extra": [ 1, 46, 166, 44, 87, 149, 175, 243, 15, 74, 60, 144, 202, 151, 238, 99, 86, 223, 79, 65, 167, 236, 26, 181, 209, 169, 197, 142, 240, 119, 195, 14, 181, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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