Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e15db69d9abc5f3625d7807c5baebb74b4fd8153f6249c7ea6422f9f3b98199

Tx prefix hash: 0366d62cae943919e09641bba88ffd268892f4ecd1fc63ee4e7d84ac9d017604
Tx public key: ce9e1ac33e39bb1ef8d8dbb2b87fa439c51c58a444ba74813576d97074a9c7e2
Timestamp: 1731503701 Timestamp [UCT]: 2024-11-13 13:15:01 Age [y:d:h:m:s]: 00:150:05:44:29
Block: 1152846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107192 RingCT/type: yes/0
Extra: 01ce9e1ac33e39bb1ef8d8dbb2b87fa439c51c58a444ba74813576d97074a9c7e20211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f701a9ff96b536b0b504001e6aa1a847e0289a684306fed4d476a45e9324ea2 0.600000000000 1638451 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": 1152856, "vin": [ { "gen": { "height": 1152846 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f701a9ff96b536b0b504001e6aa1a847e0289a684306fed4d476a45e9324ea2" } } ], "extra": [ 1, 206, 158, 26, 195, 62, 57, 187, 30, 248, 216, 219, 178, 184, 127, 164, 57, 197, 28, 88, 164, 68, 186, 116, 129, 53, 118, 217, 112, 116, 169, 199, 226, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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