Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a03cacd077f6d60ad264102a4da944d46b0964f7e30d75f01a55f4379a075a3d

Tx prefix hash: 7daa605106dd3f3df76f3d589a19a8332f1a8f027ed68c0c6809b3ecab7425d4
Tx public key: 38afb5f123d5a3af8e868735ca2233173b93c04a6f4cbdc09170e9141d1a106b
Timestamp: 1578800993 Timestamp [UCT]: 2020-01-12 03:49:53 Age [y:d:h:m:s]: 05:294:16:59:43
Block: 43623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1358554 RingCT/type: yes/0
Extra: 0138afb5f123d5a3af8e868735ca2233173b93c04a6f4cbdc09170e9141d1a106b02110000000f4ac5aa02000000000000000000

1 output(s) for total of 440.007150854000 dcy

stealth address amount amount idx
00: 431e3cd247aabcc8be21cb0e759816680a29dc74801bf8238d116cfa7983554d 440.007150854000 79095 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": 43633, "vin": [ { "gen": { "height": 43623 } } ], "vout": [ { "amount": 440007150854, "target": { "key": "431e3cd247aabcc8be21cb0e759816680a29dc74801bf8238d116cfa7983554d" } } ], "extra": [ 1, 56, 175, 181, 241, 35, 213, 163, 175, 142, 134, 135, 53, 202, 34, 51, 23, 59, 147, 192, 74, 111, 76, 189, 192, 145, 112, 233, 20, 29, 26, 16, 107, 2, 17, 0, 0, 0, 15, 74, 197, 170, 2, 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