Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0770844c70cc670f70767e523c69a8ad64a819ca7db1a701554db92145932b2b

Tx prefix hash: 7d0cc21a839c8a08c180eb1dc4cee651bd80ccce7bb68a17a53752a8b28ca5b4
Tx public key: abe5ef57f0c3e180139ca9cf5024282eb58baa892479e5b33c1b7e585b796fee
Timestamp: 1674781374 Timestamp [UCT]: 2023-01-27 01:02:54 Age [y:d:h:m:s]: 01:293:03:42:51
Block: 683539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470470 RingCT/type: yes/0
Extra: 01abe5ef57f0c3e180139ca9cf5024282eb58baa892479e5b33c1b7e585b796fee0211000000035029cbac000000000000000000

1 output(s) for total of 3.335427306000 dcy

stealth address amount amount idx
00: ab1849d06ad5ecf19e62513b9c4f8ec971da7a623a1ea24ce47fc122600ccd17 3.335427306000 1125732 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": 683549, "vin": [ { "gen": { "height": 683539 } } ], "vout": [ { "amount": 3335427306, "target": { "key": "ab1849d06ad5ecf19e62513b9c4f8ec971da7a623a1ea24ce47fc122600ccd17" } } ], "extra": [ 1, 171, 229, 239, 87, 240, 195, 225, 128, 19, 156, 169, 207, 80, 36, 40, 46, 181, 139, 170, 137, 36, 121, 229, 179, 60, 27, 126, 88, 91, 121, 111, 238, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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