Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b91e8127c5d7f4a0e89f39c81d6d45db485d979684ac48df2b63b5d7b61f3424

Tx prefix hash: 4b9d763a87969548fbaf16a9fa3110ee410a4014a9163ec54a73bc97f050e5dc
Tx public key: 79aed0cfa1f6ce5a2f78bd146a3d81b099b2cd5f9314fee50c7010330d5e7737
Timestamp: 1636074700 Timestamp [UCT]: 2021-11-05 01:11:40 Age [y:d:h:m:s]: 03:000:19:51:36
Block: 367546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 779066 RingCT/type: yes/0
Extra: 0179aed0cfa1f6ce5a2f78bd146a3d81b099b2cd5f9314fee50c7010330d5e773702110000000306faf294000000000000000000

1 output(s) for total of 37.167891467000 dcy

stealth address amount amount idx
00: 85b6f4a1a8c6aed6177abe0e7d045ae9a07ede3865d4c4d015b32977ac58d7ee 37.167891467000 745758 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": 367556, "vin": [ { "gen": { "height": 367546 } } ], "vout": [ { "amount": 37167891467, "target": { "key": "85b6f4a1a8c6aed6177abe0e7d045ae9a07ede3865d4c4d015b32977ac58d7ee" } } ], "extra": [ 1, 121, 174, 208, 207, 161, 246, 206, 90, 47, 120, 189, 20, 106, 61, 129, 176, 153, 178, 205, 95, 147, 20, 254, 229, 12, 112, 16, 51, 13, 94, 119, 55, 2, 17, 0, 0, 0, 3, 6, 250, 242, 148, 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