Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86131b1689d72337f37918d41822a0bbc28c085d9535526ac6fb34832cd9a321

Tx prefix hash: 3a3ac0f86b3736c830bfad7ee240a910c58a960eba83139b9e690545d00d0cb0
Tx public key: 7c70c4b1698f50b3849f21031e3bf2ed90c11f32c02821d5f9fa485fd6d15a63
Timestamp: 1716887197 Timestamp [UCT]: 2024-05-28 09:06:37 Age [y:d:h:m:s]: 01:003:03:20:37
Block: 1031764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263153 RingCT/type: yes/0
Extra: 017c70c4b1698f50b3849f21031e3bf2ed90c11f32c02821d5f9fa485fd6d15a630211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56e3cb628ccf2301aaa275b60b2b800eb08288406b87ae27b9675f5ec564b844 0.600000000000 1500213 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": 1031774, "vin": [ { "gen": { "height": 1031764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56e3cb628ccf2301aaa275b60b2b800eb08288406b87ae27b9675f5ec564b844" } } ], "extra": [ 1, 124, 112, 196, 177, 105, 143, 80, 179, 132, 159, 33, 3, 30, 59, 242, 237, 144, 193, 31, 50, 192, 40, 33, 213, 249, 250, 72, 95, 214, 209, 90, 99, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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