Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50d464e51b363d4e00eb11873878e0f9d9248b8d2dc37b581ee3d1f6550ffc9c

Tx prefix hash: 2d60189e8148248dc2139cbbbcb9a3d476aac71e196f1543844a0feea52d517f
Tx public key: b66053cdcadf43ed46f65ff73c54001a35eaef91a01d26d0cf20a2851a972e30
Timestamp: 1578730954 Timestamp [UCT]: 2020-01-11 08:22:34 Age [y:d:h:m:s]: 05:125:06:48:50
Block: 43147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1239684 RingCT/type: yes/0
Extra: 01b66053cdcadf43ed46f65ff73c54001a35eaef91a01d26d0cf20a2851a972e300211000000048a2ee0d9000000000000000000

1 output(s) for total of 441.607988355000 dcy

stealth address amount amount idx
00: 05a4575ef410a09878b05df5da169eb7ac727bb90fc72e5ac585324987ed5d4c 441.607988355000 78006 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": 43157, "vin": [ { "gen": { "height": 43147 } } ], "vout": [ { "amount": 441607988355, "target": { "key": "05a4575ef410a09878b05df5da169eb7ac727bb90fc72e5ac585324987ed5d4c" } } ], "extra": [ 1, 182, 96, 83, 205, 202, 223, 67, 237, 70, 246, 95, 247, 60, 84, 0, 26, 53, 234, 239, 145, 160, 29, 38, 208, 207, 32, 162, 133, 26, 151, 46, 48, 2, 17, 0, 0, 0, 4, 138, 46, 224, 217, 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