Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a29f7ed34f003c049495beb10bb0e959444b11df45c5892d046182a0c77c8cd

Tx prefix hash: a104c5f1890bb2a003c9e85b19eff3e890d15db1a554d3918f79c8b3bcb3e1cb
Tx public key: 0510dfab8475b1a9a058ea2b36054f226493c1bc4c855e964c15df1944cc1ee0
Timestamp: 1748400120 Timestamp [UCT]: 2025-05-28 02:42:00 Age [y:d:h:m:s]: 00:165:07:49:42
Block: 1292470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115833 RingCT/type: yes/0
Extra: 010510dfab8475b1a9a058ea2b36054f226493c1bc4c855e964c15df1944cc1ee0021100000001523560da000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54b170938bfed272f493fb9957ee620282ad293efeacd4a8d3584e70aafb3475 0.600000000000 1779941 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": 1292480, "vin": [ { "gen": { "height": 1292470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54b170938bfed272f493fb9957ee620282ad293efeacd4a8d3584e70aafb3475" } } ], "extra": [ 1, 5, 16, 223, 171, 132, 117, 177, 169, 160, 88, 234, 43, 54, 5, 79, 34, 100, 147, 193, 188, 76, 133, 94, 150, 76, 21, 223, 25, 68, 204, 30, 224, 2, 17, 0, 0, 0, 1, 82, 53, 96, 218, 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