Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 264e829fae2a4175b1aa15ddb367f89b2a2e976d57de6f05ffcb84b132fd8fa6

Tx prefix hash: b1b9af8cb52707e95912472a22967a0d6b35ff863786e2f2d6b9cafad70134e8
Tx public key: 5c006e85393d2fd989be879766306bbc7ff216ef755e5cadae84e1dd3eb7cb7c
Timestamp: 1631455723 Timestamp [UCT]: 2021-09-12 14:08:43 Age [y:d:h:m:s]: 03:175:04:57:12
Block: 332340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 900530 RingCT/type: yes/0
Extra: 015c006e85393d2fd989be879766306bbc7ff216ef755e5cadae84e1dd3eb7cb7c021100000014f29d7abf000000000000000000

1 output(s) for total of 48.620571820000 dcy

stealth address amount amount idx
00: 0dccc34e3dcbd40b530ea7b49ada6fd643c79e2b65a0f6813d60c92f2f958d93 48.620571820000 686337 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": 332350, "vin": [ { "gen": { "height": 332340 } } ], "vout": [ { "amount": 48620571820, "target": { "key": "0dccc34e3dcbd40b530ea7b49ada6fd643c79e2b65a0f6813d60c92f2f958d93" } } ], "extra": [ 1, 92, 0, 110, 133, 57, 61, 47, 217, 137, 190, 135, 151, 102, 48, 107, 188, 127, 242, 22, 239, 117, 94, 92, 173, 174, 132, 225, 221, 62, 183, 203, 124, 2, 17, 0, 0, 0, 20, 242, 157, 122, 191, 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