Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27f377137e3475593590275c70388ecc7d9050bf3b59c91becfcbf7e5e189ed4

Tx prefix hash: 22d9fed1aba8ccfbe8f6a08380bdc39d6006543d40ff6188a038a2e0801bd0c1
Tx public key: 20dd8749bd2da1751f253ead23b24bc8fdfd40c512f94709c9e7656a2deba7cb
Timestamp: 1577882200 Timestamp [UCT]: 2020-01-01 12:36:40 Age [y:d:h:m:s]: 04:360:19:44:33
Block: 36334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1147129 RingCT/type: yes/0
Extra: 0120dd8749bd2da1751f253ead23b24bc8fdfd40c512f94709c9e7656a2deba7cb0211000000034943cd9f000000000000000000

1 output(s) for total of 465.169496419000 dcy

stealth address amount amount idx
00: 4a09ada617736f2b1e79aa69941c2b411e7bf71a63627aac8553ce2139dcc50a 465.169496419000 61521 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": 36344, "vin": [ { "gen": { "height": 36334 } } ], "vout": [ { "amount": 465169496419, "target": { "key": "4a09ada617736f2b1e79aa69941c2b411e7bf71a63627aac8553ce2139dcc50a" } } ], "extra": [ 1, 32, 221, 135, 73, 189, 45, 161, 117, 31, 37, 62, 173, 35, 178, 75, 200, 253, 253, 64, 197, 18, 249, 71, 9, 201, 231, 101, 106, 45, 235, 167, 203, 2, 17, 0, 0, 0, 3, 73, 67, 205, 159, 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