Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78f777c82340a318833f57681938aa2e1fb65de7865f2d396caf6ea3959af9f4

Tx prefix hash: e202083ff426a09a706fff3ae97e54849a7db12b53e7058d83cee0e7aa29b7a2
Tx public key: 86beb5b1694a095f1607a990523d603181ee7d65d58e36cfe5975d1bb4609516
Timestamp: 1736838769 Timestamp [UCT]: 2025-01-14 07:12:49 Age [y:d:h:m:s]: 00:342:03:12:04
Block: 1197010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242076 RingCT/type: yes/0
Extra: 0186beb5b1694a095f1607a990523d603181ee7d65d58e36cfe5975d1bb46095160211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e44332d3ed65f0a5f786ffd8a6660fa73577af95092e3a1466c44a1a3231f8d4 0.600000000000 1683615 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": 1197020, "vin": [ { "gen": { "height": 1197010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e44332d3ed65f0a5f786ffd8a6660fa73577af95092e3a1466c44a1a3231f8d4" } } ], "extra": [ 1, 134, 190, 181, 177, 105, 74, 9, 95, 22, 7, 169, 144, 82, 61, 96, 49, 129, 238, 125, 101, 213, 142, 54, 207, 229, 151, 93, 27, 180, 96, 149, 22, 2, 17, 0, 0, 0, 5, 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