Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2640f7750da958db15da34b1767a4ea9e177baf91b0d5265524d10b2fd997224

Tx prefix hash: 457ca807b4329f5e09326b224a64a131ab916ab61895cebffd9422bc51da82ff
Tx public key: a7a2ba015d549908e254949a2a2a543708cb4f0e0807ea02b4b5dd0940573d5e
Timestamp: 1673430658 Timestamp [UCT]: 2023-01-11 09:50:58 Age [y:d:h:m:s]: 02:110:05:33:54
Block: 672334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 600472 RingCT/type: yes/0
Extra: 01a7a2ba015d549908e254949a2a2a543708cb4f0e0807ea02b4b5dd0940573d5e02110000000752542ceb000000000000000000

1 output(s) for total of 3.633108038000 dcy

stealth address amount amount idx
00: ef6897ee700e53746b0f24cfbf4f1ddc382a6324c2ad39e9a364457ee77223d9 3.633108038000 1113863 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": 672344, "vin": [ { "gen": { "height": 672334 } } ], "vout": [ { "amount": 3633108038, "target": { "key": "ef6897ee700e53746b0f24cfbf4f1ddc382a6324c2ad39e9a364457ee77223d9" } } ], "extra": [ 1, 167, 162, 186, 1, 93, 84, 153, 8, 226, 84, 148, 154, 42, 42, 84, 55, 8, 203, 79, 14, 8, 7, 234, 2, 180, 181, 221, 9, 64, 87, 61, 94, 2, 17, 0, 0, 0, 7, 82, 84, 44, 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