Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8794b43697d8ea4e6d36f70674949237094a758c0f958476945663797b7637e

Tx prefix hash: 0f1cf3bd16aa8736a959bfeaa35bdd40f97896d9891d9967f610f69e84bf1020
Tx public key: a2b6d16ed0b5a92628f43508f00170a1238ac4c1be46180d2370146a944761f9
Timestamp: 1717814282 Timestamp [UCT]: 2024-06-08 02:38:02 Age [y:d:h:m:s]: 00:321:11:48:29
Block: 1039435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229775 RingCT/type: yes/0
Extra: 01a2b6d16ed0b5a92628f43508f00170a1238ac4c1be46180d2370146a944761f9021100000008d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 448fee664b9a28f558db5a5b151306e3383f74e2bc60b29858be0ff0bc9a7c66 0.600000000000 1508074 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": 1039445, "vin": [ { "gen": { "height": 1039435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "448fee664b9a28f558db5a5b151306e3383f74e2bc60b29858be0ff0bc9a7c66" } } ], "extra": [ 1, 162, 182, 209, 110, 208, 181, 169, 38, 40, 244, 53, 8, 240, 1, 112, 161, 35, 138, 196, 193, 190, 70, 24, 13, 35, 112, 20, 106, 148, 71, 97, 249, 2, 17, 0, 0, 0, 8, 215, 73, 245, 17, 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