Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3195c747bca7b0c2e2bb67ba82ada59c9e491e3919875e51fcf4855841107999

Tx prefix hash: 9e9e77b22751ff30181e673b64c2e6b6e71fff553295ce17ddac88bba1eba0bf
Tx public key: 7842bcb84e4ab53e2fe5aef4fd730855d60eac78072277ba4f51343c6f86d327
Timestamp: 1579273701 Timestamp [UCT]: 2020-01-17 15:08:21 Age [y:d:h:m:s]: 04:346:22:49:49
Block: 47773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137273 RingCT/type: yes/0
Extra: 017842bcb84e4ab53e2fe5aef4fd730855d60eac78072277ba4f51343c6f86d32702110000000849b77a3d000000000000000000

1 output(s) for total of 426.293838672000 dcy

stealth address amount amount idx
00: 5c7a9be405a44c5a83ccb42245764273a6fd94ad219b61d60e10b7896480f41d 426.293838672000 88201 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": 47783, "vin": [ { "gen": { "height": 47773 } } ], "vout": [ { "amount": 426293838672, "target": { "key": "5c7a9be405a44c5a83ccb42245764273a6fd94ad219b61d60e10b7896480f41d" } } ], "extra": [ 1, 120, 66, 188, 184, 78, 74, 181, 62, 47, 229, 174, 244, 253, 115, 8, 85, 214, 14, 172, 120, 7, 34, 119, 186, 79, 81, 52, 60, 111, 134, 211, 39, 2, 17, 0, 0, 0, 8, 73, 183, 122, 61, 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