Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6000f2cd64e089fbd98f02cdbe4dde3da7c8d42f712ac9f87dbc100126d9282

Tx prefix hash: 59666e9e246fb81d81ead608d5ab3d715a8b4fc2b40e5b53fd346eb44abb886f
Tx public key: 58c50c2bec6543fde5401bd4e276016946cdece7cd1f6ba98b7eff729c7550f9
Timestamp: 1576425690 Timestamp [UCT]: 2019-12-15 16:01:30 Age [y:d:h:m:s]: 04:350:23:38:32
Block: 27578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1136780 RingCT/type: yes/0
Extra: 0158c50c2bec6543fde5401bd4e276016946cdece7cd1f6ba98b7eff729c7550f90211000000639159db1e000000000000000000

1 output(s) for total of 497.305776286000 dcy

stealth address amount amount idx
00: 7a4ece7692bd51e87bb39c57a8cfd829d49b7cc1010659b3484e79cad8ee4a96 497.305776286000 45592 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": 27588, "vin": [ { "gen": { "height": 27578 } } ], "vout": [ { "amount": 497305776286, "target": { "key": "7a4ece7692bd51e87bb39c57a8cfd829d49b7cc1010659b3484e79cad8ee4a96" } } ], "extra": [ 1, 88, 197, 12, 43, 236, 101, 67, 253, 229, 64, 27, 212, 226, 118, 1, 105, 70, 205, 236, 231, 205, 31, 107, 169, 139, 126, 255, 114, 156, 117, 80, 249, 2, 17, 0, 0, 0, 99, 145, 89, 219, 30, 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