Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 884a502cd727e4e6cebdd442bb67422952b7ea36b572009f7139834d2e432bde

Tx prefix hash: 837e48295649bcd3fbec787e86fbb5191b21d66e11c972d7517072e9ab07cf94
Tx public key: 593479fff5f6f4949d3a9fb673255442993c3f3782b8d84960903ac1814d89c6
Timestamp: 1574545766 Timestamp [UCT]: 2019-11-23 21:49:26 Age [y:d:h:m:s]: 04:349:06:43:06
Block: 15939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1131620 RingCT/type: yes/0
Extra: 01593479fff5f6f4949d3a9fb673255442993c3f3782b8d84960903ac1814d89c6021100000001d50ca400000000000000000000

1 output(s) for total of 543.485997355000 dcy

stealth address amount amount idx
00: aa33d7c609aa79918e6b36a30b6e5bb00cbcb60951703ef85673f047aed1f7cb 543.485997355000 21823 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": 15949, "vin": [ { "gen": { "height": 15939 } } ], "vout": [ { "amount": 543485997355, "target": { "key": "aa33d7c609aa79918e6b36a30b6e5bb00cbcb60951703ef85673f047aed1f7cb" } } ], "extra": [ 1, 89, 52, 121, 255, 245, 246, 244, 148, 157, 58, 159, 182, 115, 37, 84, 66, 153, 60, 63, 55, 130, 184, 216, 73, 96, 144, 58, 193, 129, 77, 137, 198, 2, 17, 0, 0, 0, 1, 213, 12, 164, 0, 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