Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7a2076be9ded21ed20075f8bfdb4dd49a3a435c5417c8f25545459fb52546e9

Tx prefix hash: f602c4e059a88e34686243d86b63009689f3b2d87784b077baf010b56012cd90
Tx public key: 73fb521051279243370e34e7f40df4c0a0fa7900edea5016963d260a56308c9f
Timestamp: 1695587964 Timestamp [UCT]: 2023-09-24 20:39:24 Age [y:d:h:m:s]: 01:192:05:19:50
Block: 855363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398439 RingCT/type: yes/0
Extra: 0173fb521051279243370e34e7f40df4c0a0fa7900edea5016963d260a56308c9f02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.899140069000 dcy

stealth address amount amount idx
00: b51a7fe14e1f23a333c2b2b2ffd027990dfb2674766d5543d7a585d1cb44cf0c 0.899140069000 1309381 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": 855373, "vin": [ { "gen": { "height": 855363 } } ], "vout": [ { "amount": 899140069, "target": { "key": "b51a7fe14e1f23a333c2b2b2ffd027990dfb2674766d5543d7a585d1cb44cf0c" } } ], "extra": [ 1, 115, 251, 82, 16, 81, 39, 146, 67, 55, 14, 52, 231, 244, 13, 244, 192, 160, 250, 121, 0, 237, 234, 80, 22, 150, 61, 38, 10, 86, 48, 140, 159, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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