Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 168eebb6210b98510ecdb1fee52c36c2c20135f733512ca0ff8789e1c79ccab6

Tx prefix hash: 36934a796c9c917da1993b9779096cb66145797615b817dec8922c691f713b75
Tx public key: 2748e906ad775d5635de52d6e2afd5369cc9d289f3d7632c9ff1ad4448e9a9c6
Timestamp: 1618190622 Timestamp [UCT]: 2021-04-12 01:23:42 Age [y:d:h:m:s]: 04:007:04:44:24
Block: 237906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1026046 RingCT/type: yes/0
Extra: 012748e906ad775d5635de52d6e2afd5369cc9d289f3d7632c9ff1ad4448e9a9c60211000000496eb9c26a000000000000000000

1 output(s) for total of 99.935372082000 dcy

stealth address amount amount idx
00: dd3e3e13d38f72d13ccca505af40b322e88d2be85aeecf8a03ee1acce627f922 99.935372082000 495170 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": 237916, "vin": [ { "gen": { "height": 237906 } } ], "vout": [ { "amount": 99935372082, "target": { "key": "dd3e3e13d38f72d13ccca505af40b322e88d2be85aeecf8a03ee1acce627f922" } } ], "extra": [ 1, 39, 72, 233, 6, 173, 119, 93, 86, 53, 222, 82, 214, 226, 175, 213, 54, 156, 201, 210, 137, 243, 215, 99, 44, 159, 241, 173, 68, 72, 233, 169, 198, 2, 17, 0, 0, 0, 73, 110, 185, 194, 106, 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