Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a27259b5f9a120d4209226f853e1ad0066c3f9611ac0ce656e3fb40f090f861

Tx prefix hash: 5e0358a2f351c5c70c8f3672f9da89a64d658b0ed3dd3ea0c05b527df595bc9a
Tx public key: 354bb4042b8c1027a4bb1c54a298a8355270a10e8808c796d1fe1f7af0ca0d47
Timestamp: 1710713193 Timestamp [UCT]: 2024-03-17 22:06:33 Age [y:d:h:m:s]: 01:236:03:03:27
Block: 980584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427437 RingCT/type: yes/0
Extra: 01354bb4042b8c1027a4bb1c54a298a8355270a10e8808c796d1fe1f7af0ca0d47021100000002a5df9d86000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd5b075ba36e14c4cb81dbb8f55f2a17f0d39a4bc225281553fcf254849cf7e2 0.600000000000 1440659 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": 980594, "vin": [ { "gen": { "height": 980584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd5b075ba36e14c4cb81dbb8f55f2a17f0d39a4bc225281553fcf254849cf7e2" } } ], "extra": [ 1, 53, 75, 180, 4, 43, 140, 16, 39, 164, 187, 28, 84, 162, 152, 168, 53, 82, 112, 161, 14, 136, 8, 199, 150, 209, 254, 31, 122, 240, 202, 13, 71, 2, 17, 0, 0, 0, 2, 165, 223, 157, 134, 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