Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b351db2e186f83714991de02f2b11b4640cd54e3187f07dd02a59beac2bc053f

Tx prefix hash: dd13b6ac9caf7680bb5a99bb839741c575ebeed1c4966c27052789d26022aef3
Tx public key: 9e43d70c82e744ed5d595903d5d1a03e63ba83919ea9e0ee5501acff010ef6d4
Timestamp: 1682313458 Timestamp [UCT]: 2023-04-24 05:17:38 Age [y:d:h:m:s]: 01:356:12:13:07
Block: 745361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516071 RingCT/type: yes/0
Extra: 019e43d70c82e744ed5d595903d5d1a03e63ba83919ea9e0ee5501acff010ef6d4021100000001e7ace25d000000000000000000

1 output(s) for total of 2.081180763000 dcy

stealth address amount amount idx
00: 05cfde7181328e2a5d9dfa21e931a5d9e3cda7f760e6ddabb555bdb0181209e4 2.081180763000 1192804 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": 745371, "vin": [ { "gen": { "height": 745361 } } ], "vout": [ { "amount": 2081180763, "target": { "key": "05cfde7181328e2a5d9dfa21e931a5d9e3cda7f760e6ddabb555bdb0181209e4" } } ], "extra": [ 1, 158, 67, 215, 12, 130, 231, 68, 237, 93, 89, 89, 3, 213, 209, 160, 62, 99, 186, 131, 145, 158, 169, 224, 238, 85, 1, 172, 255, 1, 14, 246, 212, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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