Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81b50688cf9c438cd434368162622fd25667bdc8f495b5a32b3870e867ae785e

Tx prefix hash: e72c325df6b02200495b98f7ca26475bc2e8c26723e9ffc00c436399c4a115d4
Tx public key: 536813aad771552ff61c6aaac8f52f90a6e510a257e411f5f4150aece8dfda78
Timestamp: 1701452988 Timestamp [UCT]: 2023-12-01 17:49:48 Age [y:d:h:m:s]: 01:083:22:32:26
Block: 903783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321108 RingCT/type: yes/0
Extra: 01536813aad771552ff61c6aaac8f52f90a6e510a257e411f5f4150aece8dfda7802110000000533af99f4000000000000000000

1 output(s) for total of 0.621429292000 dcy

stealth address amount amount idx
00: e2d14d3fb834062c73e0f7c74bcd51cb6a10c2e6e518b48a0a59d5a2f4d60425 0.621429292000 1360474 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": 903793, "vin": [ { "gen": { "height": 903783 } } ], "vout": [ { "amount": 621429292, "target": { "key": "e2d14d3fb834062c73e0f7c74bcd51cb6a10c2e6e518b48a0a59d5a2f4d60425" } } ], "extra": [ 1, 83, 104, 19, 170, 215, 113, 85, 47, 246, 28, 106, 170, 200, 245, 47, 144, 166, 229, 16, 162, 87, 228, 17, 245, 244, 21, 10, 236, 232, 223, 218, 120, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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