Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d677603ac7d1751c390b482e5c33007cda8b52a46d8130f2e2fd598164be7d2

Tx prefix hash: 2ea8e3f714f0f9b966fa9f4ff4ed1fc3de282087bdf33d8bfcb81e86ce5176b8
Tx public key: 9f21610e6ab172089f8438dfb4ee3d75ece191b0670446b323e7d0f8f5924744
Timestamp: 1700825749 Timestamp [UCT]: 2023-11-24 11:35:49 Age [y:d:h:m:s]: 01:154:01:14:59
Block: 898588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371292 RingCT/type: yes/0
Extra: 019f21610e6ab172089f8438dfb4ee3d75ece191b0670446b323e7d0f8f5924744021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.646554174000 dcy

stealth address amount amount idx
00: a8fd6363c9bdbde4424669adc05c725a59cf90d4f3f07bd9d4f0ce185f593425 0.646554174000 1355009 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": 898598, "vin": [ { "gen": { "height": 898588 } } ], "vout": [ { "amount": 646554174, "target": { "key": "a8fd6363c9bdbde4424669adc05c725a59cf90d4f3f07bd9d4f0ce185f593425" } } ], "extra": [ 1, 159, 33, 97, 14, 106, 177, 114, 8, 159, 132, 56, 223, 180, 238, 61, 117, 236, 225, 145, 176, 103, 4, 70, 179, 35, 231, 208, 248, 245, 146, 71, 68, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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