Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92e2aa107992175a3c4dbe8941450ceb2eaed93cf076aea407af3fa64c97b76e

Tx prefix hash: cdcbf91dc2f3dac18b598e7774cd1693e5f56157eb9459fe1806b84cdef38e00
Tx public key: c3bb91fa8d95be8b56b1439ab6e3149894c7b2b67262e76698e7d6814df9a1a4
Timestamp: 1708354823 Timestamp [UCT]: 2024-02-19 15:00:23 Age [y:d:h:m:s]: 01:117:03:27:39
Block: 961013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344696 RingCT/type: yes/0
Extra: 01c3bb91fa8d95be8b56b1439ab6e3149894c7b2b67262e76698e7d6814df9a1a40211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af2703e6eacedae9aefd4286c0ecb4082e78a8661c83dd0ddb17590fad0bfb47 0.600000000000 1420600 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": 961023, "vin": [ { "gen": { "height": 961013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af2703e6eacedae9aefd4286c0ecb4082e78a8661c83dd0ddb17590fad0bfb47" } } ], "extra": [ 1, 195, 187, 145, 250, 141, 149, 190, 139, 86, 177, 67, 154, 182, 227, 20, 152, 148, 199, 178, 182, 114, 98, 231, 102, 152, 231, 214, 129, 77, 249, 161, 164, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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